On 11 Sep., 17:07, GreyWyvern <s...@greywyvern.com> wrote:
> Please explain.
>
> What if I don't *want* to print your calendar backgrounds. Then you
> aren't giving me a choice.
That's correct! My client already has an application that produces her
calendars as PDF. She usually snail mails them out, after she prints
them. To free up time on her behave I'm creating a web based
application that does just that. The caveat (not sure if that's the
correct term) is that she is afraid that her clients will call her and
ask for the "real" calendar if the web based one doesn't look like the
existing or look worse (less graphic). Thus not achieving anything. To
put it short, the clients will continue to get the calendar as always
but they will have to print it out themselves.
*
The calendar is NOT public and the user WILL have JS turned on and
their browsers WILL support CSS. If the have anything worse than IE6
then it's too bad.
*
If any of your guys are CSS sharks I would very much appreciate your
with the scrollbar issue.
Regards, Jon.

Jon wrote:
> On 11 Sep., 16:58, Jerry Stuckle <jstuck...@attglobal.net> wrote:
>> But since you're writing everything in javascript, it's impossible to tell.
> Jerry, you can use firebug and click on the HTML tab. That will show
> you the generated HTML. For you sake I will create a page with the
> generated HTML. I will post the URI shortly :-)
>

Yes, you can, but it's a lot harder to read - and difficult to read and
save.

But I think you missed my point. Get a static page going first, then
get it to work with your JS.

And I agree with John. I think this would be better as a table. It is
a table, after all.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

And lo, Jon didst speak in alt.www.webmaster:

> GreyWyvern wrote:
>
>> Please explain.
>>
>> What if I don't *want* to print your calendar backgrounds. Then you
>> aren't giving me a choice.
>
> That's correct! My client already has an application that produces her
> calendars as PDF. She usually snail mails them out, after she prints
> them.

If she already has an application that produces her calendars as PDF, why
not just email the PDF? What is the benefit of moving away from that
application to reproduce the calendar in HTML?

Grey

--
The technical axiom that nothing is impossible sinisterly implies the
pitfall corollary that nothing is ridiculous.
- http://www.greywyvern.com/orca#search - Orca Search: Full-featured
spider and site-search engine

Jon wrote:

> My client already has an application that produces her
> calendars as PDF. She usually snail mails them out, after she prints
> them. To free up time on her behave I'm creating a web based
> application that does just that.

Except, not in PDF format.


> The caveat (not sure if that's the
> correct term) is that she is afraid that her clients will call her and
> ask for the "real" calendar if the web based one doesn't look like the
> existing

If you create a page intended to be printed in HTML, you are at the
mercy of the browser. Each browser will place the HTML on the printed
page slightly differently. Even the same browser with different settings
will give slightly different results. If everybody's printed copy must
look the same, you pretty much have to go with PDF.

For everyone who doesn't like JS generated pages:
http://www.bookevent.dk/JSCalendar/JustHTML.htm

Hmm.. So far all the time I have used on this topic on usenet has been
about answering questions that had little to do with my question. I'm
sorry but I didn't post a question to answer questions about design
decisions or whatever else people could come up with. My project is
set, I have the design goals, I have a contract with my client that
specifies everything. It's not up to debate and nothing will be
changed. I do think usenet groups can be awarding in that you can get
another pair of eyes on a subject. But this has been a complete waste
of time.. Not only did I come up with a solution to my problem alone,
I also wasted time answering question from people who didn't have an
answer. This is all very sad, because this could really be a great,
professional assistance in those hairy moments where you don't know
what to do. I don't know what to do about it, but it's probably the
last time I will post any questions here.

For all of you who read this, please think again before you reply to a
topic/question. A question about why my client don't use another
application is really really pointless. I wouldn't be creating an
application if there was no need or if my client wasn't paying. The
simple answer to THAT question is that there is more to my application
than just the calendar. Which IS really really beside the point. My
question is about browser behavior and CSS. Nothing more and nothing
else!

Thanks for your time. I hope you will think twice before asking
questions to a question. We are all professionals and we all loose
money on wasting time.
Regards, Jon.

PS. Please don't tell me it's easier to manipulate tables than divs -
I had to learn the hard way and there is no way I'm switching back to
tables if I can avoid it!

And lo, Jon didst speak in alt.www.webmaster:

> Hmm.. So far all the time I have used on this topic on usenet has been
> about answering questions that had little to do with my question. I'm
> sorry but I didn't post a question to answer questions about design
> decisions or whatever else people could come up with. My project is
> set, I have the design goals, I have a contract with my client that
> specifies everything. It's not up to debate and nothing will be
> changed. I do think usenet groups can be awarding in that you can get
> another pair of eyes on a subject. But this has been a complete waste
> of time.. Not only did I come up with a solution to my problem alone,
> I also wasted time answering question from people who didn't have an
> answer. This is all very sad, because this could really be a great,
> professional assistance in those hairy moments where you don't know
> what to do. I don't know what to do about it, but it's probably the
> last time I will post any questions here.

If your perception of Usenet is as nothing more than an information desk,
good riddance.

Usenet is a collaborative medium where everyone can voice their ideas. If
you have a problem with the discussion drifting to elements of your
problem you don't think are important, you should have phrased your
question in such a way as to provide the initial focus.

You had a "solution" to your problem decided upon from the beginning, you
only needed to know how to implement it. Yet instead you outlined your
entire situation then expected people to ignore all that context and just
give you the goods. Then when people began suggesting different (and
better) ways to resolve your situation, you got pissy about people wasting
your time. In case you haven't figured it out already, that makes you
pretty arrogant.

> For all of you who read this, please think again before you reply to a
> topic/question. A question about why my client don't use another
> application is really really pointless. I wouldn't be creating an
> application if there was no need or if my client wasn't paying. The
> simple answer to THAT question is that there is more to my application
> than just the calendar. Which IS really really beside the point. My
> question is about browser behavior and CSS. Nothing more and nothing
> else!

I'm sorry, but who are you? I ask because it sounds like you expected
your reputation and client history to have preceded you. I'm sorry to
dissappoint you, but it didn't. We have no clue at what point your
project is at, and what kind of urgency you require. How are we supposed
to know what still can or cannot be changed?

BTW, most of the suggestions offered you are indeed *better* solutions to
your problem. Don't blame us if what you really wanted was a quick hack
rather than valuable with the fundamental design.

> Thanks for your time. I hope you will think twice before asking
> questions to a question. We are all professionals and we all loose
> money on wasting time.
> Regards, Jon.

If it was a question of money, you should have gone to Experts-Exchange or
Yahoo! Answers. On Usenet, for a problem as general as you described it,
you're going to get a roundtable discussion as a response, and you're
being foolish to have expected anything else.

> PS. Please don't tell me it's easier to manipulate tables than divs -
> I had to learn the hard way and there is no way I'm switching back to
> tables if I can avoid it!

Oh yeah, that's exactly how I was going to end this post, with a comment
on how you should really be using tables. But it seems like you predicted
precisely what I was going to say. Now I am totally at a loss for words.
Looks like you win this one.

Grey

--
The technical axiom that nothing is impossible sinisterly implies the
pitfall corollary that nothing is ridiculous.
- http://www.greywyvern.com/orca#search - Orca Search: Full-featured
spider and site-search engine

Jon wrote:
> Hmm.. So far all the time I have used on this topic on usenet has been
> about answering questions that had little to do with my question. I'm
> sorry but I didn't post a question to answer questions about design
> decisions or whatever else people could come up with.

Your original post explored three different possible ways to solve your
problem. Exploring different ways to solve the problem was not out of line.

> My project is
> set, I have the design goals, I have a contract with my client that
> specifies everything. It's not up to debate and nothing will be
> changed.

Does the contract specify that a printable calendar must be created in
HTML with no tables?

> I do think usenet groups can be awarding in that you can get
> another pair of eyes on a subject. But this has been a complete waste
> of time.. Not only did I come up with a solution to my problem alone,
> I also wasted time answering question from people who didn't have an
> answer.

We did have answers. They weren't the answers you wanted, but they were
good answers.

> For all of you who read this, please think again before you reply to a
> topic/question. A question about why my client don't use another
> application is really really pointless. I wouldn't be creating an
> application if there was no need or if my client wasn't paying. The
> simple answer to THAT question is that there is more to my application
> than just the calendar. Which IS really really beside the point. My
> question is about browser behavior and CSS. Nothing more and nothing
> else!

Then why did your original question explore other options?

Your client has a calendar in PDF format. Your client wants other users
to obtain the same calendar. You mentioned that PDF was a possibility. I
suggested that it was the best option, and it could easily be done by
someone who knew how to do it.

And now you complain because it wasn't the answer you wanted.

Take it from someone who has been there. At some point someone will
email you and tell you that on X browser and Y operating system the page
won't print as expected.

> Thanks for your time. I hope you will think twice before asking
> questions to a question. We are all professionals and we all loose
> money on wasting time.

We are all professionals. Some of us have been there and done that. We
have learned the right way and the wrong way to do things. Exploring
better options is part of what we do here.

Jon wrote:

> But this has been a complete waste
> of time.. Not only did I come up with a solution to my problem alone

Maybe not. Two of the 5 browsers I have on my computer don't print the
calendar correctly.