Why not just preview in osu! then?XinCrin wrote:
In my opinion, I would like the option to add a section where we can see a betmap with skin created, to see if the skin looks good while you're playing or not
Why not just preview in osu! then?XinCrin wrote:
In my opinion, I would like the option to add a section where we can see a betmap with skin created, to see if the skin looks good while you're playing or not
- Fixed UserSettings-CrashIts available here: http://www.kagurame.bioside.de
- Fixed ForceUpdate (button with no text in Options)
- Added new Grafik Engine (No lags while hovering some elements, better caching and faster view of graphics)
- Added Listed-Section (Listing all file names of a skin to change them at once)
- Added mouse selection list (not designet yet)
- Added change mouse cursor
- Added file loading routine (its showing some numbers if it finnished, this is for debugging)
- Added a view of the current action (in the upper left corner of the application)
How to test?
Click Options, the blocked elements will be unblocked (its a bug at this time )
Click "Listed", then "Button1" (no name at this moment, its only for testing)
Select a new cursor (Click into the right center to be able to scroll in your mouse buttons, auto select doesnt works this time)
- New Updater (the old updater will delete all files in subfolders)The update is uploading to the server and should be available in a few minutes.
- Removed some debug code
- Reading skin files from Skins and Songs folder
- Fixed bug with wrong application path for osu!
- Saving you osu! directory in user settings now
- Fixed rare crash while initializing cursor selection
- Added first try of designing mouse cursor selection
If you get a message box, you can ignore this message.
This messages will be added in overview later with functions to fix the reported problem.
I could guide you through using GitHub, it's really easy to set up projects there and keeping them up-to-date.Kagurame wrote:
Thanks for the link.
But i´m developing under Ruby now, and a good code base if programmed and functionally (i only dont understand github xD), so i dont need the dite at the moment. But thanks
Can u teach me? if it's okay with youKagurame wrote:
if you want to learn a bit i could show you ruby, its really easy to use.
If you understand ruby than you could help if you want
Notes to osc dev directory
NOTIFY
OSCStub.exe will start Game.exe and other important stuff (see source code or following documentation)
Game.exe will start the programm.
At this time osc is not multilanguage. It will be reimplemented later
DIRECTORIES
.git git hub system directoy (don´t tuch!)
Audio contains required Audio files. Loading from this in Lib/System/Audio.rb
Data contains the main code - this loading additional code
Graphics contains required graphics - sorted in sub directories. most of sub folders are obsulete!
Graphics/SkinFiles the default osu! skin
Kagurame userfolder dev system win 7 Kagu-chan
Kai userfolder dev system win xp Kagu-chan
Lib contains the main code - see Lib/Load.rb for details. Lib/Run.rb runs the code
Shared contains language files and temp dir
Shared/Temp maybe obsulete!
StubDev contains the dev files of the stub. Look in source for more details or following documentation of this
VBDev Other obsulete! Old dev dir of skin reader. Skin reader is implemented in stub now. Will be deleted if stub is working!
Messages interface Stub => OSC
Tasks interface OSC => Stub
osuSkins temp skin directory from stub. Stub analize skin files and puts files here. OSC catch scin files from there to user folder
FILES
.gitattributes git hub system file (don´t tuch!)
.gitignore git hub system file (don´t tuch!)
Game.exe OSC main app. Dont start it manually.
Game.ini ini file for osc. Version info and required script files stored here.
Game.rxproj main engine file from osc. Don´t tuch!
Homescreen Script.txt design skript.
PlayerInstall.rar required rgss player installation directory. unpack and install to use osc.
README.md git hub system file (don´t tuch!)
Test-script.txt design coding and testing file.
Todo kagu.txt germand notifications for main developer
osusk.ico main icon of osc.
Game_original.exe backup file. obsulete!
OSCStub_original.exe backup file. obsulete!
OSCStub.exe osc stub. run this to run osc!
NOTES this file.
Data/Scripts.rxdata main code of osc. include load and run routines and keyboard adresses (don´t tuch!)
USERFOLDER
OSC_Skin contains nothing normally. Copy own files in this to overrite osc graphics or create default files for skins. Looking for correct filename!
SkinData contains stored skin preferences (file lists). (don´t tuch!)
Log.txt user´s log file. send me this file if you have some errors or problems. Will be overwritten each osc start.
SkinCache.skd complete osu skin files file list. (don´t tuch!)
startup.ini this configuration file for osc. will be load at first.
usersettings.ini your settings.
STUB STUFF
* analize osu skin files at begin
* copy analized skin file lists to user folder
* finding out osu install directory
* creating user folder with default files
OSCStub is controlled via special task files in tasks directory. Don´t create files by hand.
OSCStub is creating special notes files in messages directory. Don´t create files by hand.
OSCStub ends automatically if OSC stopped.
OSC don´t stop if OSCStub stopped.
Osu could startet from OSCStub, right-clicking notify bar icon and select your function.
Left-clicking the icon brings OSC to foreground and get system focus on it.
FILE EXTENSIONS
*.skd skin filelists. Its an acronym to SKin Data. Normally it contains big file lists of your osu skin files and story board files.
UPCOMING UPDATESYSTEM
osc load all his code and then don´t need the directory "Lib". So OSCStub will update files if OSC running. Replace old files and
send a message via Messages directory interface - OSC notify user for new version. Only restart osc. A function to restart OSC
will be implemented in OSCStub, but no auto restart function. OSCStub looking in intervalls for updates and maybe the user is working
on a skin which is not compiled.
OSCStub will update via an integrated updater (not implemented at this time).
The update path will be changable in Game.ini file. OSC copy it self to temp directory of the computer system.
This copy will startet with special parameters, this copy download new files. At programm ending (normally) or forced at start(special
notes in update files) the update files will be changed to programm files (renaming). OSC stub will have a minimal file size.
OSC FILE SIZE
A lot of dev copies (skin related) existing. So the directory size is over 100 mb at this time.
The using version will contains the rgss player (23 mb), code files and osc graphics (~1 mb) and the template skin files (~ 10 mb,
will be sorted out for skinnable and not skinnable files).
So osc has in real a file size of ~~ 35 mb, the maximum i´m thinking about is 50 mb.
139,5 kb of this used by code - the rest been graphics or created own files (e.g. *.skd)
+29.06.2013
+removed some dev code from vb projects and some files from there. Removed OsuSkinReader (unused now)
+
+
+29.06.2013
+removed unused class variable from plugin script. Also removed old accessor (id)
+
+
+29.06.2013
+Fixed loading bug in plugins. Deactivated plugins are now accessible in the application.
+
+
+29.06.2013
+Changed Load.rb-Pattern of PlugIns. So description is in this file and a name of a settingsclass (could booth be clear strings)
+
+
+30.06.2013
+changed reg key for osu! to the correct value (win 7 / xp / vista etc.
+
+
+30.06.2013
+removed old temp dir clearing routine
+
+
+30.06.2013
+removed old read_files_recursively-routine (unused)
+
+
+30.06.2013
+removed externals directory and code file - unused
+
+
+30.06.2013
+added "activate_back_button" for Context_Base (activate it, call update - super and overwrite exit to exit the current context)
+
+
+30.06.2013
+added PlugIns-section into options. Not Implemented Message at this time
+
+
+30.06.2013
+removed a old obsolete marked function
+
+
+30.06.2013
+removed senseless print and p calls
+
+
+30.06.2013
+added infotext to back button in skin scenes
+
+
+04.07.2013
+added console debug output
+
+
+04.07.2013
+redirect print & p to console (puts)
+
+
+04.07.2013
+p & print could be deactivated or activated ($___p; $___print)
+
+
+04.07.2013
+added object debug inspect method (puts - console)
+
+
+06.07.2013
+added exception logging and logging to debug console
+
+
+06.07.2013
+add plugins scene
+
+
+06.07.2013
+click on osu dir in options opens your osu directory in explorer now
+
+
+07.07.2013
+added settings to example plugin
+
+
+08.07.2013
+button "change skin type" now working
+
+
+08.07.2013
+added load skin context
+
+
+08.07.2013
+removed disposing issue in scene skin (context startup)
+
+
+10.07.2013
+added scrollable skin select preview class (SkinContainer)
+
+
+10.07.2013
+removed senseless and buggy code from window_base
+
+
+10.07.2013
+disbaled plugin view when no plugins installed
+
+
+10.07.2013
+VERSION (NAME: 'Osu! Skin Creator V0.9.13.128') PUBLISHED ON 10.07.2013
Kagu-chan wrote:
Sorry for long time without response by me ._.
In my sommer holidays i lost a lot of my work - because my laptop crashed.
The last version is this on git hub.
Currently i´m in planing phase - a better concept is required because ruby is so slow.
I´m working on, but have to do a lot privat for highschool planned in march.
Sorry and greeting, Kagu-chan.
New ideas - New technic
The third technic at this time, i know.
But i remarked that Ruby is simply to slow for this type of application.
The last few weeks i testet a lot and now i will try out a new way.
It will be a Visual Basic application again.
This application download the current API version from a web server. Graphics will be drawn with HTML / CSS.
The layout will be the same - but new functions will be available:
Because the api is stored on a server, the software always runs with the newest version. If there are required local files, it could be simply downloaded at runtime.
Visual Basic could simply interact with the servers - so it will give a login (optionally) to store some settings global for you (you can work on more computers with same settings without transporting more than the small app). Also you can share your skins directly with the app or look for other skins from other users.
A support system will be integratet - With the application you can report bugs or take future requests - Notifications about this will be shown at startup for you (if you are an user) and some other peoples (if you want to see future requests they will be shown in the application).
Change log entries will be shown one time at startup if you´re registrated.
The app could be runned offline, shure. But one time it has to be runned with internet to catch the latest API files.
You could download the louncher here: LINK.
At best the application has a own directiory.
Greetings, Kagu-chan.