2005-06-11, 01:24
hi,
it's time to ask people for some help. it will not be about coding at this point. i sorta like doing things on my own, although the final product might suffer. the idea was that people can improve on my code later - that might sound stupid, but co-working on code can be quite the mess too...especially since i come up with how things should be as i code it.
what i really need help for is suggestions for a name and design. the name scriptservice is perhaps not the best, and it was actually more of a random name i thought about when introducing the idea to you. scriptbrowser is one suggestion, but i'd like more.
also, i'd like comments on the design. these are some early suggestions on the installer part:
the bright bar at the bottom is a download progress bar. changes color after status etc and position after progress (doh). the rounded status bar above this will slide in and out when theres activity. is there something that would be crucial to an installer? button help etc will be on it's own screen, activated by whatever button i find left over.
please keep in mind that this is the installer part. i might do that one "completely done" first and release it, as waiting for me to finish the browser part too might take a while.
also note that the theme is far from done. the background will change, as will most other things too i guess .
there is also another thing i'd like to know. in the script specifications...i somehow need to know what file to execute when there's more than one .py file. this could be solved by <execute> tags or something like that in the script.xml , or it could be solved by everyone using a standard name on the main .py file, like script.py . the advantage with the first method is that i can write tags to script.xml on scripts that isn't specs compatible, so that it remembers what file it should run even though the scripts doesn't follow the specs. please reply with suggestions...i don't want to make decisions myself without getting some input from the community.
the xml so far:
it's time to ask people for some help. it will not be about coding at this point. i sorta like doing things on my own, although the final product might suffer. the idea was that people can improve on my code later - that might sound stupid, but co-working on code can be quite the mess too...especially since i come up with how things should be as i code it.
what i really need help for is suggestions for a name and design. the name scriptservice is perhaps not the best, and it was actually more of a random name i thought about when introducing the idea to you. scriptbrowser is one suggestion, but i'd like more.
also, i'd like comments on the design. these are some early suggestions on the installer part:
the bright bar at the bottom is a download progress bar. changes color after status etc and position after progress (doh). the rounded status bar above this will slide in and out when theres activity. is there something that would be crucial to an installer? button help etc will be on it's own screen, activated by whatever button i find left over.
please keep in mind that this is the installer part. i might do that one "completely done" first and release it, as waiting for me to finish the browser part too might take a while.
also note that the theme is far from done. the background will change, as will most other things too i guess .
there is also another thing i'd like to know. in the script specifications...i somehow need to know what file to execute when there's more than one .py file. this could be solved by <execute> tags or something like that in the script.xml , or it could be solved by everyone using a standard name on the main .py file, like script.py . the advantage with the first method is that i can write tags to script.xml on scripts that isn't specs compatible, so that it remembers what file it should run even though the scripts doesn't follow the specs. please reply with suggestions...i don't want to make decisions myself without getting some input from the community.
the xml so far:
Quote:<info>
<name>xbmclyrics</name>
<author>enderw</author>
<version>1.0</version>
<updated>05-05-20t15:16:12</updated> #will be written to by script with data from site
<description>fetches lyrics from the song you are currently listening to. uses lyrc.com.ar as a base. some more information could be here i'm sure, but i can't come up with any at the moment.</description>
<changelog>xx-xx-xx: added animations on startup and end.</changelog>
<firstrun>this will be displayed on first run</firstrun>
<execute>xbmclyrics.py</execute> <---good or not?
</info>