You will never know when your code will hit a compiler you did not anticipate. Keep it cleanand simpleand don't try to be smart. Consistency is key in writing alot of components. Avoid using tricks because their value will decrease over time because you will lose track of the tricks you used.
2. Using a 'better' language (C++, C#) will not reduce the real complexity which is the number of components you need to write and thier dependencies and relationships.
3. Consistency in API function and component naming is sometimes more important than the implementation itself since the implementation can be refactored while an API mostly cannot be changed.
Just a few things that come to mind when writing code for Screens. I am still active on the project and spend between 1-2 hours a day on Screens now thanks to my HP Mini-Note 2133.
I have not got to the graphics code just yet, but I am very close to try it out.
8 comments:
any luck with the graphics component?
Hi. Hows the move going? Also I'm just wondering your estimated time until development can resume.
The move date is august 5th. But I am still working on something to make me get quickly up to speed on the code when I get back coding. Full time job is also very demanding at the moment which leaves me very little time for anything else.
Hi. I recently tried to send you the Unicode font converter by email so you can have it for safe keeping, but it seems like it didn't go through...
Hi.
How have things been lately? Anything new?
Hi. Its been a while since we last heard from you. Whats the latest?
So is anything going to happen with ScreensOS?
Hi. Do you have any news/updates or at least some editorials for us?
...Please?
Post a Comment