域卡的卜 Vicker’s Blog

PROTOTYPE 0.4

Vicker | January 28, 2006 | 1:01 pm

Is been a while since the last prototype. It is because this version’s scope is pretty large which involves all the possible page elements that will be present in the web page.Same as the previous navigation menu, all the page content elements are constructed through the XML data file. The page content elements supported now includes:- Basic text with text formats- Images files like JPEG, GIF, PNG- Multimedia file like SWF- Background color and background image- Rectangles of different appearance for framing- Text or graphic linkings- Linkings further divided into internal Flash and external HTTP linksThe next step will be implementing the editor (Action) part of these page elements, hopefully will be completed after Lunar New Year. And this will probably named as Release 1.

PROTOTYPE 0.3

Vicker | January 16, 2006 | 12:51 am

After the text problems… is better to get back to the track. The prototype 0.3 is finally finished~~!! With the well written message box class, all the messages like system error, notification or tooltips can be shown to the user in a clear way.The function here is simple.- When a message appears, the message box will pop out at the bottom.- After a few seconds, it will disappear.- If user rolls over, it will appear again.- Clicking on it will bring out the message history with corresponding timestamps.- Clicking again will just reverse the result.The next prototype will be working on more important page contents which should be a easier way to go. (I hope so…)Furthermore, with the better knowledge in textformats and stylesheets. The working principle of the WYSIWYG text editor which will be used for the editing of text contents is already in my mind.The brief mechanism is to use the textformat class. It involves the catching of user’s highlighting area and applying the formats. And at last it can be used to export back HTML codes which can be used in the HTML section of the project.

TEXTFORMAT and STYLESHEET

Vicker | | 12:26 am

Before talking about the already finished prototype 0.3, I think it is better to pin point on the two troublesome items as stated in my heading. That is the TEXTFORMAT and STYLESHEET classes within Flash.The reason that I want to talk about these is that these two little item (seems like little…) troubles me a whole week to work on it. I dont know why, however it seems that Macromedia do have a lot of bugs in these two classes.First, let me introduce these two classes.TEXTFORMAT- A class that is used to apply text formats to a textfield on the stage- It can be applied to the whole textfield, or a portion of it if specified- Adv: It is easy to use and flexible because you can apply on anywhere- Dis: It is hard to maintain and it requires great programming effortSTYLESHEET- Alternative approach to apply text formats- Apply to be whole textfield- Adv: It is surely easy to maintain. Further it can be reused for HTML section- Dis: The text content need to attach many tags in order to apply stylesheetsOkay, actually coding in both approarch is very simple. However there are tons of bugs came out which makes me crazy within this week. So I better mention in the web somewhere to let others preventing these traps.If you are using dynamic textfields with embedded character, you CANNOT use STYLESHEET NOR TEXTFORMAT with FONT-FAMILY settings!!- I put this one so seriously because this bug takes me nights to discover!!!!- If you violate this, the text will simply not displaying… which you will never know that it is related to FONT-FAMILY until you delete your codes line by line…- The possible reason probably is that embedded character will only embed for the current font, so… changing it will make the text simply gone…- For the same reason… If you want to set Bold, Italic, etc. You HAVE to set it in the textfield beforehand. This will make sure that the embeded character will also embed those styles.* Dynamic textfield means that the content of the textfield is defined by external codings.* Embedded characters are essential for animations on textfields.And what I can suggest for future development is that…If you use dynamic textfields… try not to put animations… it will drive you crazy…

PROTOTYPE 0.3 (HALF WAY)

Vicker | January 2, 2006 | 12:07 pm

Original planning is that this version will focusing on the system messaging function. However when I just started working on it, I found that a scroll bar is essential for this component to work. Although there are a lot of scroll bar components in the market already, I prefer to write my own. (Kind of stupid… ya?) First, just to challenge myself and knowing the working mechanism. Second, allowing me to change the style and skin of the scroll bar in my own will.So half way of this version is dedicated to the scroll bar component. Actually you will never know that the scroll bar is extremely complex unless you self written one.Say for an example.- How to calculate the size of the scroll box?- How to calculate the distance that the scroll box travel for each scrolling line?- How to make the scroll box “chasing” the mouse?- How to make the scroll move once when the arrow is pressed, wait for a little moment and continuously scrolling until mouse up?This little scroll bar takes me two working days… but is worth. At least I learned much within.The next step will continue the message box~By the way, Happy 2006~!!

PROTOTYPE 0.4

Related posts

PROTOTYPE 0.3

Related posts

TEXTFORMAT and STYLESHEET

Related posts

PROTOTYPE 0.3 (HALF WAY)

Related posts

Meta

Certification

Adobe MAX 2008

Categories

Archives

Tag Cloud

Flickr

Blogroll

FxAIR.org