fofredux-devel

[Fofredux-devel] error on install

[Evan R. <eva...@gm...>]

hey guys,
i've just grabbed the latest from svn, and am trying to install into a new
db to do some testing, but i get an error:


*Fatal error*: fatal flex scanner internal error--end of buffer missed in *
<path>\lib\api\rpc_map.php* on line *32

*what's strange is that line 32 is the last comment in that file, which is
being included somewhere from install.php


i'm currently on my dev box (which is windows with php5.1.1).  do i need to
activate any specific php modules for the rpc stuff (which i assume is
blowing up)?  and why is this stuff even needed on installing anyway?

/evan

Re: [Fofredux-devel] error on install

[Kevin <ke...@dr...>]

> hey guys,
> i've just grabbed the latest from svn, and am trying to install into a new
> db to do some testing, but i get an error:
>
>
> *Fatal error*: fatal flex scanner internal error--end of buffer missed in
> *
> <path>\lib\api\rpc_map.php* on line *32
>
> *what's strange is that line 32 is the last comment in that file, which is
> being included somewhere from install.php

I have never seen this before but Google was helpful.  Apparently the PHP
source parser does not like it when the last token in the file is a
comment.  I added a few blank lines to the file to fix.  Please update and
retest.

I don't get this error in my dev environment.  (php 5.1.6 on Linux)  It
could be your php version, or windows.

*elapse 10 mins*

I dug into php's CVS.  This problem only happens in version 5.1.1  It was
fixed in 5.1.2.



--
Kevin

Re: [Fofredux-devel] error on install

[Evan R. <eva...@gm...>]

yep, fix works for me.  it's about time that i upgrade xampp on my
machine...

but it was good to get this one fixed, since 5.1.1 was stuck in a xampp
release for a long time, so it could have caused a bunch of problems for
users.

i'm going to take a stab at doing a pda viewer then...

here's my plan...even if this stuff only pans out for my own personal use
(and i'm not giving any time estimate, since i'm stuck developing 50+ hrs a
week at work)...
1 item viewed at a time...with a few commands on the bottom:
Mark Read & Next
Skip to Next
Skip to First

i'll do an async fetch for the next item, so the "mark read & next" would
actually replace the contents of a <p> and send a hit a web service to mark
the item read, while prefetching the next item.  I think this should reduce
the amount of wait for the reader, and allow us to send only the necessary
data down to the device (the feed item)
my only hurdle will probably be windows mobile 5.0's version of IE's
handling of the ajax stuff.  even though all the sdk's at msdn claim that it
should work.


what's the status on ajax libs?  i see we have prototype in the tree, but
are we using it yet?  i may throw yahoo in there for my purposes, since i
know it very very well, and don't want to waste energy learning something
new.  although, prototype could be attractive if it's simple to do the async
calls, since it's probably much lighter weight than the yahoo libs,
especially when we don't need the ui extras yet.

/evan


On 3/5/07, Kevin <ke...@dr...> wrote:
>
>
> > hey guys,
> > i've just grabbed the latest from svn, and am trying to install into a
> new
> > db to do some testing, but i get an error:
> >
> >
> > *Fatal error*: fatal flex scanner internal error--end of buffer missed
> in
> > *
> > <path>\lib\api\rpc_map.php* on line *32
> >
> > *what's strange is that line 32 is the last comment in that file, which
> is
> > being included somewhere from install.php
>
> I have never seen this before but Google was helpful.  Apparently the PHP
> source parser does not like it when the last token in the file is a
> comment.  I added a few blank lines to the file to fix.  Please update and
> retest.
>
> I don't get this error in my dev environment.  (php 5.1.6 on Linux)  It
> could be your php version, or windows.
>
> *elapse 10 mins*
>
> I dug into php's CVS.  This problem only happens in version 5.1.1  It was
> fixed in 5.1.2.
>
>
>
> --
> Kevin
>
>

Re: [Fofredux-devel] error on install

[Kevin <ke...@dr...>]

Evan Roth wrote:
> ...
>
> what's the status on ajax libs?  i see we have prototype in the tree, 
> but are we using it yet?  i may throw yahoo in there for my purposes, 
> since i know it very very well, and don't want to waste energy 
> learning something new.  although, prototype could be attractive if 
> it's simple to do the async calls, since it's probably much lighter 
> weight than the yahoo libs, especially when we don't need the ui 
> extras yet.
>
There is also api.php which provides a proxy for xml-rpc and json-rpc.  
I currently only have test methods implemented, but it's pretty easy to 
add more.  The nice part about the json-rpc part is the javascript 
client stub functions/methods are auto-generated.  Just define a php 
function on the server, and then use the function in javascript code.

-Kevin

Re: [Fofredux-devel] error on install

[Andrew T. <ajt...@hi...>]

On 3/5/07, Evan Roth <eva...@gm...> wrote:
> but it was good to get this one fixed, since 5.1.1 was stuck in a xampp
> release for a long time, so it could have caused a bunch of problems for
> users.

I'll update the RC package.

> i'm going to take a stab at doing a pda viewer then...
>
> here's my plan...even if this stuff only pans out for my own personal use
> (and i'm not giving any time estimate, since i'm stuck developing 50+ hrs a
> week at work)...
> 1 item viewed at a time...with a few commands on the bottom:
> Mark Read & Next
> Skip to Next
> Skip to First

You may be able to just have a CSS change for Mobile and choose to
view 1 item at a time in an add'l preferences. Would be worth trying
as a first stab.

I think I would personally also prefer an option to see 5 titles at a
time and select to view specific items. But the 1/item at a time is
good start.

> i'll do an async fetch for the next item, so the "mark read & next" would
> actually replace the contents of a <p> and send a hit a web service to mark
> the item read, while prefetching the next item.  I think this should reduce
> the amount of wait for the reader, and allow us to send only the necessary
> data down to the device (the feed item)
> my only hurdle will probably be windows mobile 5.0's version of IE's
> handling of the ajax stuff.  even though all the sdk's at msdn claim that it
> should work.

don't target IE - someone can come back and fix it later :) target
Opera for mobiles or something for testing. More devices supported.

>
> what's the status on ajax libs?  i see we have prototype in the tree, but
> are we using it yet?  i may throw yahoo in there for my purposes, since i
> know it very very well, and don't want to waste energy learning something
> new.  although, prototype could be attractive if it's simple to do the async
> calls, since it's probably much lighter weight than the yahoo libs,
> especially when we don't need the ui extras yet.
>

I tossed prototype in there to start - and it's what I know. But
others suggested Yahoo as well, and may be a good fit. So if you start
using it, go ahead and put it in there for now, and maybe we can use
some of your stuff back in the full UI.

Andrew

Re: [Fofredux-devel] error on install

[Evan R. <eva...@gm...>]

On 3/6/07, Andrew Turner <ajt...@hi...> wrote:
>
>
> I think I would personally also prefer an option to see 5 titles at a
> time and select to view specific items. But the 1/item at a time is
> good start.


well, we could push something to the options, if the whole attempt becomes
worthwhile.  it will really vary on what the user is actually reading.  some
of the blog entries i pull down can get pretty long.

> i'll do an async fetch for the next item, so the "mark read & next" would
> > actually replace the contents of a <p> and send a hit a web service to
> mark
> > the item read, while prefetching the next item.  I think this should
> reduce
> > the amount of wait for the reader, and allow us to send only the
> necessary
> > data down to the device (the feed item)
> > my only hurdle will probably be windows mobile 5.0's version of IE's
> > handling of the ajax stuff.  even though all the sdk's at msdn claim
> that it
> > should work.
>
> don't target IE - someone can come back and fix it later :) target
> Opera for mobiles or something for testing. More devices supported.


IE is what i have to test, since my device (Samsung Blackjack) is win mobile
5.0.  it does a reasonable job browsing most sites. kind of cross between
pda and mobile.

/evan