Detail view for website has dummy stats

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Navigate to detail view for website
2.
3.

What is the expected output? What do you see instead?
Should see site specific out put instead of profanity and ellipses

Please use labels and text to provide additional information.

Original issue reported on code.google.com by andrewps...@gmail.com on 12 Apr 2009 at 6:05

[GoogleCodeExporter]

Original comment by andrewps...@gmail.com on 14 Apr 2009 at 1:34

• Changed state: Started

[GoogleCodeExporter]

Added
http://code.google.com/p/monarch-flex/source/browse/trunk/monarch-server/Client/
detailStats.php,
a skeleton for returning all data requested by the GUI. Posts per day is the 
only
functioning statistic so far.

Original comment by andrewps...@gmail.com on 14 Apr 2009 at 5:19

[GoogleCodeExporter]

Ryan has finished
http://code.google.com/p/monarch-flex/source/browse/trunk/monarch-server/Client/
detailStats.php
and I have added basic GUI support. 
TODO: formatting in GUI, make URLs full on back-end

Original comment by andrewps...@gmail.com on 15 Apr 2009 at 4:50

[GoogleCodeExporter]

Can you use a tree for the keyword stats? 

http://livedocs.adobe.com/flex/2/langref/mx/controls/Tree.html

Original comment by tokyotech on 16 Apr 2009 at 12:26

[GoogleCodeExporter]

I've gotten some success with the tree, so I'll be working on the keywords 
stuff now.

Original comment by tokyotech on 16 Apr 2009 at 12:39

[GoogleCodeExporter]

The only thing left now is UI stuff. The links are now working after a back-end 
change.

Original comment by andrewps...@gmail.com on 16 Apr 2009 at 1:23

• Changed state: Fixed

[GoogleCodeExporter]

Submitted some preliminary work on the keyword stats.  I don't know how to do 
the 
following:

1) Just show all the keywords initially without having to open "root2".
2) Link to the threads and users.
3) Could private var keywords:XML just have been set to the server XML response 
instead of me writing all this redundant code that converts the server XML into 
another form of XML?

Original comment by tokyotech on 16 Apr 2009 at 3:58

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

First of all, here are the reasons I kept things as a Text component and 
populated
the htmlText attribute:
1) That was the way it was.
2) Linking to websites is trivial. Clicking a link will open your default 
browser and
take you to a page.
3) It was simple and quick, given the time constraint.

The markup sucked but generally when working with HTML, even the limited form
supported by mx:Text, it is much more flexible than Flex components. Oh well, I 
will
try to help you with getting this working. With lots of keywords the tree will 
be
easier to navigate than a scrollable page. 

For (3), the server response is returned as an ArrayCollection by default but 
adding
"e4x" or "xml" for resultFormat of the HTTPService will change how result is
deserialized
(http://livedocs.adobe.com/flex/2/langref/mx/rpc/http/HTTPService.html#resultFor
mat).
Using "e4x", I can output the event.result and it looks like XML but I can't do
anything with this object. 
For (1), I'm guessing that the 'showRoot' attribute of mx:Tree is meant to take 
care
of this. I don't know for (2). May have to fuck with event handlers and crap, I 
don't
know.

Original comment by andrewps...@gmail.com on 16 Apr 2009 at 6:29

[GoogleCodeExporter]

I submitted changes that fix problems (1) and (3). Will look at (2) now.

Original comment by andrewps...@gmail.com on 17 Apr 2009 at 12:03

[GoogleCodeExporter]

Oops, looks like there was a problem with conflicts. Fixing...

Original comment by andrewps...@gmail.com on 17 Apr 2009 at 12:49

[GoogleCodeExporter]

TODO: 1) beautification of page, 2) address links section, 3) Decide on how to 
display 'General' stats.

Original comment by andrewps...@gmail.com on 17 Apr 2009 at 3:03

[GoogleCodeExporter]

I styled the general portion. 

I called the server again without the e4x format (as was done in your first 
version),
but couldn't figure out why the statResultHandler2 was not being executed. Man, 
this
is as far as I can get with Flex...

Original comment by tokyotech on 18 Apr 2009 at 4:24

[GoogleCodeExporter]

This looks good. I think I fixed the issues with the 'General stats' part. Once
again, it took several attempts to figure out something that worked where the 
types
aligned and everything. No need for statsHandler2.

Original comment by andrewps...@gmail.com on 19 Apr 2009 at 7:58

[GoogleCodeExporter]

After updating my SVN, I still see two result handlers and there's a dangling 
else on
line 187...

Original comment by tokyotech on 19 Apr 2009 at 3:04

[GoogleCodeExporter]

Disregard the last comment.  Everything started working after Mariusz's recent 
commit.

Original comment by tokyotech on 19 Apr 2009 at 5:16

[GoogleCodeExporter]

This issue is functionally working now, but visually not appealing.

Original comment by tokyotech on 20 Apr 2009 at 5:55

[GoogleCodeExporter]

Original comment by tokyotech on 24 Apr 2009 at 1:23

• Changed state: Done